feat: MCPB desktop extension for sem-ai#63
Open
skipi wants to merge 1 commit into
Open
Conversation
skipi
force-pushed
the
mk/sem-ai/mcpb-extension
branch
2 times, most recently
from
c094dcd to
33c40ad
Compare
Bundle the `sem-ai mcp` stdio server as a one-click MCPB (.mcpb) extension for Claude Desktop and other MCPB-aware apps. - config: SEMAPHORE_HOST / SEMAPHORE_API_TOKEN env vars override ~/.sem.yaml, so the install dialog can inject credentials (token kept in the OS keychain) and the same vars configure the CLI in CI. - mcpb/manifest.json: binary server type, user_config (host + sensitive token) mapped to env, win32 .exe platform override. - packaging is folded into GoReleaser: a build post-hook runs the official `mcpb pack` (scripts/mcpb-pack.sh) on each freshly built binary, and release.extra_files attaches dist/*.mcpb to the release — one bundle per OS+arch (platform_overrides keys on OS, not arch). The post-hook skips snapshot builds (the -next suffix), so PR/snapshot pipelines stay node-free; only the release job installs mcpb and packs. - `make mcpb` builds a local bundle for the current platform into dist/. - CI: PR pipeline validates mcpb/manifest.json via `mcpb validate`. - version-synced as a 4th manifest via release.sh + check-manifest-versions.sh. - install.sh points Claude Desktop users to the bundle. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
skipi
force-pushed
the
mk/sem-ai/mcpb-extension
branch
from
33c40ad to
311dafb
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Package the
sem-ai mcpstdio server as a one-click MCPB (MCP Bundle) desktop extension. Claude Desktop (and other MCPB-aware apps) install a.mcpb, the user enters their org host + API token in the install dialog, and the app launchessem-ai mcpfor them — no terminal, nogo install, no~/.sem.yamlediting. Same server the Claude Code / Codex plugin already uses; MCPB is just a different delivery wrapper around it.How it works
The bundle injects the user's config as environment variables, which
config.Load()now reads (env wins over~/.sem.yaml, so the same vars also configure the plain CLI in CI):user_confighostSEMAPHORE_HOSTapi_token(sensitive → OS keychain)SEMAPHORE_API_TOKENAt runtime Claude Desktop runs
server/sem-ai mcpwith those env vars set; the cobra tree is exposed as MCP tools over stdio, exactly as today.Packaging
One bundle ships per OS+arch — MCPB
platform_overrideskeys on OS only, not CPU architecture.scripts/pack-mcpb.shruns after GoReleaser in the release pipeline: it downloads each published release archive, drops the binary underserver/, zips it withmanifest.jsonat the root, and uploads the.mcpbfiles back to the tag. Packing runs after publish and is idempotent (--clobber), so a bundling hiccup never blocks or corrupts the CLI release — just re-runscripts/pack-mcpb.sh <tag>.mcpb/manifest.jsonis version-synced as a 4th manifest viascripts/release.shand guarded byscripts/check-manifest-versions.sh, so the bundle version can never drift from the CLI / plugin version.Testing
pkg/config/config_test.go: file-context, env-only, env-overrides-file, blank-env-falls-back — all pass.initializehandshake through the bundled binary — returns the expectedserverInfo.mcpb validate mcpb/manifest.jsonpasses the schema.bash -non all scripts;check-manifest-versions.shandrelease.sh --dry-runexercised with the new 4th manifest.🤖 Generated with Claude Code